We have obtained information on how to resolve this issue. Solution: static embeded framework Embeded framework with static library copy own to app bundle, but the main binary will be replaced by some sort of stub from the original and remove unneeded resources(e.g. Headers). This allows you to tie a static library to a specific necesserary resource on framework form. Thus, the solution steps are as follows: transform our static library to static embeded framework.(framework target but "Mach-O Type: static Library" in Xcode setting) putting them together in xcframework. I hope Apple makes this well known...

Hi. So your team re-created all the static libraries with static frameworks?? Yes. Our library is not that large, so it wasn't that big of a deal. Sorry, but I don't have any better information myself.